Global platform for managing subscriber identity modules

ABSTRACT

A method of operating a mobile wireless network comprising: receiving, by a provisioning server, a signal from a mobile wireless network specifying a location of a first mobile device having a first International Mobile Subscriber Identity (IMSI) and operating in the mobile wireless network under a first condition, the mobile wireless network including a plurality of mobile switching centers (MSCs) and a plurality of mobile devices operating in the mobile wireless network; provisioning the first IMSI in the first HLR based on a state transition rule from a first provisioning state to a second provisioning state; provisioning a second IMSI in the first HLR based on the state transition rule from a third provisioning state to the first provisioning state; and transmitting data identifying the second IMSI to the first mobile device to allow the first mobile device to operate in the mobile wireless network under a second condition.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.13/622,172 entitled GLOBAL PLATFORM FOR MANAGING SUBSCRIBER IDENTITYMODULES filed on Sep. 18, 2012, which is a continuation of U.S. patentapplication Ser. No. 13/340,997 entitled GLOBAL PLATFORM FOR MANAGINGSUBSCRIBER IDENTITY MODULES filed on Dec. 30, 2011, now U.S. Pat. No.8,275,357, issued on Sep. 25, 2012, U.S. patent application Ser. No.11/119,401 entitled SELF PROVISIONING OF WIRELESS TERMINALS IN CELLULARNETWORKS filed Apr. 29, 2005, now issued as U.S. Pat. No. 8,346,214,issued on Jan. 1, 2013, U.S. patent application Ser. No. 11/398,493entitled SELF PROVISIONING OF WIRELESS TERMINALS IN WIRELESS NETWORKSfiled Apr. 4, 2006, now issued as U.S. Pat. No. 8,498,615, issued onJul. 30, 2013, and co-pending U.S. patent application Ser. No.11/804,582 entitled WIRELESS COMMUNICATION PROVISIONING USING STATETRANSITION RULES filed May 18, 2007.

BACKGROUND OF THE INVENTION

In a wireless system, the wireless terminal has a Subscriber IdentityModule (SIM), which contains the identity of the subscriber. One of theprimary functions of the wireless terminal with its SIM in conjunctionwith the wireless network system is to authenticate the validity of thewireless terminal (for example, a cell phone) and the wirelessterminal's subscription to the network. The SIM is typically a microchipthat is located on a plastic card, a SIM card, which is approximately 1cm square. The SIM card is then placed in a slot of the wirelessterminal to establish the unique identity of the subscriber to thenetwork. In some cases, the wireless terminal itself contains thesubscriber identification and authentication functionality so that aseparate SIM and/or SIM card is not utilized.

In the SIM (or within the wireless terminal) an authentication key and asubscriber identification pair are stored. An example of such a pairwould be the authentication key Ki as used in GSM networks and theassociated subscriber identification IMSI (International MobileSubscriber Identity). Another example would be the authentication keyA-Key and subscriber identification MIN (Mobile Identification Number)as used in CDMA and TDMA networks. In either case, a correspondingidentical set of an authentication key and a subscriber identificationare stored in the network. In the SIM (or in the wireless terminal) andwithin the network, the authentication functionality is run using thelocal authentication key and some authentication data which is exchangedbetween the SIM and the network. If the outcomes of running theauthentication functionality in the SIM and in the network leads to thesame result, then the SIM/wireless terminal are considered to beauthenticated for the wireless network.

In existing wireless systems, a SIM (or wireless terminal) has anauthentication key associated with only one subscriber identificationand this subscriber identity is typically tied to a local region ornetwork. When a SIM (or wireless terminal) authenticates in a regionthat is not local or with a network that is not local, then usually theSIM (or wireless terminal) needs to pay additional roaming servicecharges to connect with the wireless network. It would be beneficial ifthe SIM (or wireless terminal) were not tied to a local region ornetwork. For example, equipment vendors would then be able to sell thesame equipment in multiple regions and for multiple networks.Additionally, end users may avoid roaming service charges or at leastmore favorable subscription terms may be available.

BRIEF DESCRIPTION OF THE DRAWINGS

Various embodiments of the invention are disclosed in the followingdetailed description and the accompanying drawings.

FIG. 1 illustrates an embodiment of a self-provisioning wireless system.

FIG. 2A illustrates an example of authentication data structures in oneembodiment.

FIG. 2B illustrates an example of authentication data structures inanother embodiment.

FIG. 3 is a flow diagram illustrating an embodiment of a process foracquiring wireless service from a wireless network.

FIG. 4A illustrates an embodiment of a process for provisioning orauthentication of a wireless terminal in a network system.

FIG. 4B illustrates another embodiment of a process for provisioning orauthentication of a wireless terminal in a network system.

FIG. 5 illustrates an embodiment of a process for self-provisioning orauthentication, of a wireless terminal in a network system.

FIG. 6 is a flow diagram illustrating an embodiment of a process foracquiring wireless service from a wireless network.

FIG. 7 illustrates a block diagram of an embodiment of a system formobile data communication provisioning.

FIG. 8 is a flow diagram illustrating an embodiment of a process formobile data communication provisioning.

FIG. 9 is a block diagram illustrating an embodiment of a statedefinition.

FIG. 10 illustrates an embodiment of a state transition rule definition.

FIG. 11 is a flow diagram illustrating an embodiment of states of achannel sale model for provisioning and the transitions between thestates.

FIG. 12 is a flow diagram illustrating an embodiment of states of aretail sale model for provisioning and the transitions between thestates.

FIG. 13 is a flow diagram illustrating an embodiment of a process forprovisioning wireless communication.

DETAILED DESCRIPTION

The invention can be implemented in numerous ways, including as aprocess, an apparatus, a system, a composition of matter, a computerreadable medium such as a computer readable storage medium or a computernetwork wherein program instructions are sent over optical, electronicor wireless communication links. In this specification, theseimplementations, or any other form that the invention may take, may bereferred to as techniques. A component such as a processor or a memorydescribed as being configured to perform a task includes both a generalcomponent that is temporarily configured to perform the task at a giventime or a specific component that is manufactured to perform the task.In general, the order of the steps of disclosed processes may be alteredwithin the scope of the invention.

A detailed description of one or more embodiments of the invention isprovided below along with accompanying figures that illustrate theprinciples of the invention. The invention is described in connectionwith such embodiments, but the invention is not limited to anyembodiment. The scope of the invention is limited only by the claims andthe invention encompasses numerous alternatives, modifications andequivalents. Numerous specific details are set forth in the followingdescription in order to provide a thorough understanding of theinvention. These details are provided for the purpose of example and theinvention may be practiced according to the claims without some or allof these specific details. For the purpose of clarity, technicalmaterial that is known in the technical fields related to the inventionhas not been described in detail so that the invention is notunnecessarily obscured.

Provisioning of Subscriber Identifications to Wireless Terminals inWireless Networks

A system and method for provisioning a subscriber identification to awireless terminal in a wireless network is disclosed. A control centerreceives transmission from a wireless network. The transmissionindicates that a wireless terminal is roaming. The control centerprovisions a subscriber identification to the wireless terminal, wherethe subscriber identification is selected based at least in part on theidentification of the wireless network in which the wireless terminal isroaming. Using the newly-provisioned subscriber identification, thewireless terminal acquires wireless service from the wireless network asa local wireless terminal. The wireless terminal can operate as a localwireless terminal for that network, or for a network with which thelocal network has a preferred relationship. The wireless terminal canacquire telecommunications service as a local terminal by using a storedset of authentication key-subscriber identification that is specific tothe network it is operating in. In various embodiments, the wirelessterminal can operate as a local terminal by receiving or downloading aspecific set of authentication key-subscriber identification, or byreceiving or downloading a subscriber identification to pair with anexisting authentication key.

FIG. 1 illustrates an embodiment of a wireless system. In the exampleshown, the wireless system includes a plurality of wireless terminals,represented in FIG. 1 by wireless terminal 100, a plurality of wirelessnetwork base stations, represented by wireless network base stations104, wireless network center 106, Home Location Register/AuthenticationCenter (HLR/AuC) 108, and provisioning server 110 capable ofprovisioning the wireless terminals. Although only one wireless networkcenter 106 is shown, it is understood that the wireless system caninclude multiple wireless network centers 106. Each wireless networkcenter 106 includes, or is associated with, a HLR, a Mobile SwitchingCenter/Visitor Location Register (MSC/VLR) and a Serving GPRS ServiceNode (SGSN), or Packet Data Serving Node (PDSN). In one embodiment, themultiple wireless centers 106 may be operated by different networkcarriers, while HLR/AuC 108 and provisioning server 110 are operated bya global platform provider. Wireless terminal 100 includes a SubscriberIdentity Module (SIM) which is either an attachable hardware card with amemory and a processor or a software object embedded in the wirelessterminal. Wireless terminal 100 communicates with wireless network basestations 104 using wireless signal 102. As a wireless terminal movesaround it communicates with different wireless base stations. Wirelessnetwork base stations 104 communicate with wireless network center 106.

Communications from a wireless terminal are passed to another wirelessterminal over the same wireless network using a local wireless networkbase station to the other wireless terminal or the communications arecarried by a wired network or other wireless network to the destinationterminal. Wireless network center 106 communicates with its associatedHLR, where sets of authentication key-subscriber identification arestored, to help in authenticating a wireless terminal that is acquiringwireless network service. One example of a subscriber identification isan international mobile subscriber identifier (IMSI). Wireless networkcenter 106 and its associated HLR communicate with provisioning server110 to enable a wireless terminal to acquire a new subscriberidentification that is paired with an existing authentication key and/ora new set of authentication key-subscriber identification. In someembodiments the transmission of the authentication key or theauthentication key-subscriber identification is encrypted. In variousembodiments, the authentication key or the authentication key-subscriberidentification is/are decrypted at the wireless terminal and/or in theSIM card. The old authentication key-new subscriber identification pairand/or the new set of authentication key-subscriber identification areadded in the appropriate manner to the HLR/AuC 108 databases or the HLRdatabases associated with wireless network centers 106 so that thewireless terminal can be authenticated and can acquire wireless networkservice using the new subscriber identification and/or authenticationkey set. In various embodiments, the wireless network system is acellular system, a GSM/GPRS wireless system, a CDMA or WCDMA wirelesssystem, or a TDMA wireless system, or any other type of wireless networksystem.

FIG. 2A illustrates an example of authentication data structures in oneembodiment. In some embodiments, the authentication data structure for awireless terminal is located in the SIM, and for the network in theHLR/AuC such as HLR/Auc 108 of FIG. 1 or the HLR associated withwireless network centers 106. An authentication data structure (ADS) fora wireless terminal includes an authentication key (AK) and one or moresubscriber identifications (SI) and is used to help authenticate awireless terminal for a wireless network. In the example shown, the ADSfor wireless terminal 1 includes one authentication key and onesubscriber identification. The ADS for wireless terminal 2 includes oneauthentication key and three subscriber identifications. The ADS forwireless terminal N includes one authentication key and two subscriberidentifications. The ADS for network includes the authenticationkey-subscriber identification entries for each of the wirelessterminals. Entries for wireless terminal 1, 2, and N are shown. In someembodiments, there are more than one authentication keys where eachauthentication key has multiple subscriber identifications.

FIG. 2B illustrates an example of authentication data structures inanother embodiment. Authentication data structure (ADS) for a wirelessterminal includes a Ki and one or more IMSI's. In the example shown, theADS for wireless terminal 1 includes one Ki and one IMSI. The ADS forwireless terminal 2 includes one Ki and three IMSI's. The ADS forwireless terminal N includes one Ki and two IMSI's. The ADS for HLR/AuCincludes the Ki-IMSI entries for each of the wireless terminals. Entriesfor wireless terminal 1, 2, and N are shown.

FIG. 3 is a flow diagram illustrating an embodiment of a process foracquiring wireless service from a wireless network. In some embodiments,the process of FIG. 3 is implemented on a wireless terminal such aswireless terminal 100 in FIG. 1. In the example shown, in 300 a wirelesssignal is received from a wireless network. A wireless terminal receiveswireless signals from a nearby network base station. In 302, a networkidentification is decoded from the wireless signal. The wireless signalincludes a mobile network identification. For example, the wirelessterminal scans for the existing wireless system signals. When it finds anetwork system broadcast control channel (e.g. BCCH in GSM Systems), itdecodes the broadcasted information to decode the Location AreaIdentifier (LAI). The LAI is composed of a mobile country code, a mobilenetwork code and a location area code. From the LAI, the wirelessterminal can determine the country in which it is operating. In 304, asubscriber identification is selected based on the decoded networkidentification. For example, LAI information can be matched with thesubscriber identification of the wireless terminal, which includes amobile country code, a mobile network code, and a mobile subscriberidentification number. In various embodiments, the LAI mobile countrycode and subscriber identification mobile country code are matched orthe LAI mobile network code and the subscriber identification mobilenetwork code are matched. In various embodiments, the selection of asubscriber identification is based at least in part on the pricing ofdifferent wireless networks, the billed account for that connection, abilled account for the wireless service, the application that will usethe connection, an application using the wireless service (for example,one subscriber identification for data communication and a differentsubscriber identification for voice communication) or any otherappropriate criteria for selecting a subscriber identification. In 306,wireless service is acquired from the wireless network.

FIG. 4A illustrates an embodiment of a process for provisioningsubscriber identification to a wireless terminal in a network system.Referring also to FIG. 1, in the example shown, wireless terminal 100receives information from and transmits information to wireless networkcenter 106 (and its associated HLR), HLR/AuC 108, and provisioningserver 110 using wireless signals 102. As shown in FIGS. 4A and 4B,wireless network center 106 (and its associated HLR), HLR/AuC 108, andprovisioning server 110 are collectively identified by numeral 402. In404, wireless terminal 100 listens to wireless signals 102 transmittedfrom network base stations 104 and decodes the mobile networkidentification from the transmitted information. For example, thewireless terminal scans for the existing wireless system signals. Whenit finds a network system broadcast control channel (e.g. BCCH in GSMSystems), it decodes the broadcasted information to decode the LocationArea Identifier (LAI). The LAI is composed of a mobile country code, amobile network code and a location area code. From the LAI, the wirelessterminal can determine the country in which it is operating. Thewireless terminal receives a set of Subscriber Identification fromnetwork center, HLR/AuC, and provisioning server 402 and stores in itsADS. In 406, the wireless terminal chooses a Subscriber Identificationwith the same country code from its ADS. For example, the SubscriberIdentification is composed of a mobile country code, a mobile networkcode, and mobile subscriber identification number. The codes in theSubscriber Identification can be used to match a SubscriberIdentification to the local network and/or country. The rest of theSubscriber Identifications stored in the wireless terminal's ADS may bemade inactive for the duration of the session.

In 408, the wireless terminal performs a location update with thevisited wireless network using the new Subscriber Identification. In410, the network center, HLR/AuC, and provisioning server 402 searchesfor the Subscriber Identification in its ADS and retrieves thecorresponding Authentication Key. In 412, a challenge is generated(RAND) and with the Authentication Key is used to calculate a Response(SRES) using an authentication algorithm (A3). In 414, the RAND is sentto the wireless terminal and a response is requested. In 416, thewireless terminal uses the RAND with the Authentication Key from its ADSto independently calculate a SRES using encryption algorithm (A3) storedin its SIM. In 418, the SRES is sent to the network center and/orHLR/AuC and/or provisioning server 402. In 420, authentication is passedif the received SRES matches the locally computed SRES, otherwise theauthentication fails.

FIG. 4B illustrates another embodiment of a process for provisioningsubscriber identification to a wireless terminal in a network system. Insome cases, the wireless terminal will not contain an IMSI that matchesthe country code of the local network system. The wireless terminal canconnect to the network using an IMSI with another country code and thenreceiving or downloading a local IMSI (i.e. with a matching countrycode). In the example shown, wireless terminal 400B receives informationfrom and transmits information to the network center, HLR/AuC, andprovisioning server 402B using cellular signals. In 404B, wirelessterminal 400B listens to cellular signals transmitted from networktowers and decodes the country code from the transmitted information. In406B, wireless terminal 400B communicates, after being authenticated,with the provisioning server transmitting information including acountry code and a terminal producer. In 408B, the provisioning serverchooses a new IMSI with a local country code. In 410B, the new IMSI isadded to the ADS of the HLR/AuC (or the HLR associated with the networksystem) corresponding to the wireless terminal (i.e. paired with thewireless terminal's Ki). In 412B, the provisioning server sends the newIMSI to wireless terminal 400B. In 414B, wireless terminal 400B adds thenew IMSI to its ADS. In 416B, wireless terminal 400 reestablishes itsconnection with the network system with the new IMSI as the active IMSI.In some embodiments, depending on the information transmitted (i.e. IMSIrange or type of wireless terminal), communication may be establishedbetween the wireless terminal and a specific application server (i.e., aglobal platform provider's provisioning server or another server). Insome embodiments, this communication with a specific application serveris encrypted.

FIG. 5 illustrates an embodiment of a process for provisioningsubscriber identification to a wireless terminal in a network system. Insome embodiments, the wireless terminal will not contain a SubscriberIdentification that matches the network code and/or country code of thelocal network system. The wireless terminal can connect to the networkusing a Subscriber Identification with another network/country code andthen receiving downloading a local Subscriber Identification (i.e. witha matching country code). Referring also to FIGS. 1 and 4A, in theexample shown, wireless terminal 100 receives information from andtransmits information to network center 106 (and its associated HLR),HLR/AuC 108, and provisioning server 110 using wireless signals 102. In504, wireless terminal 100 listens to wireless signals transmitted fromnetwork base stations 104 and decodes the mobile network identificationfrom the transmitted information similar to 404 of FIG. 4A. In 506,wireless terminal 100 communicates, after being authenticating using aprocess similar to 408-420 of FIG. 4A, with the provisioning server 110transmitting information including a country code and a terminalproducer. In 508, the provisioning server 110 chooses a new SubscriberIdentification with a local country code and/or network code. In 510,the new Subscriber Identification is added to the ADS of the HLR/AuC 108or the HLR associated with the visited network corresponding to thewireless terminal (i.e. paired with the wireless terminal'sAuthentication Key). In 512, the provisioning server 110 sends the newSubscriber Identification to wireless terminal 500. In 515, wirelessterminal 100 adds the new Subscriber Identification to its ADS. In 516,wireless terminal 100 reestablishes its connection with the networksystem with the new Subscriber Identification as the active SubscriberIdentification. In some embodiments, depending on the informationtransmitted (e.g., subscriber identification range or type of wirelessterminal), communication may be established between the wirelessterminal and a specific application server (e.g., a global platformprovider's provisioning server or another server). In some embodiments,this communication with a specific application server is encrypted.

FIG. 6 is a flow diagram illustrating an embodiment of a process foracquiring wireless service from a wireless network. In the exampleshown, in 600 a wireless signal is received from a wireless network. In602, wireless service is acquired from the wireless network using afirst subscriber identification. In 604, information is transmitted tothe wireless network. In 606, a second subscriber identification, whichis selected by an application server (or provisioning server 110 of FIG.1), is received. The second subscriber identification is selected basedat least in part on one or more of the following: the wireless network,the wireless network identification, the base station that the wirelessterminal is communicating with, the local country associated with thenetwork, or any other appropriate criteria for selecting a subscriberidentification. In various embodiments, the first subscriberidentification and the second subscriber identification are both pairedwith a single authentication key or the first subscriber identificationis paired with a first authentication key and the second subscriberidentification is paired with a second authentication key. In someembodiments, a second authentication key is received. In variousembodiments, the subscriber identification and/or the authentication keyare received after having been encrypted and need to be decrypted afterhaving been received. In some embodiments, the subscriber identificationis encrypted and decrypted using an authentication key. In variousembodiments, a subscriber identification and/or a authentication key isencrypted in an application server, in a provisioning server, in awireless network server, or in a combination of anapplication/provisioning server and a wireless network server, or in anyother appropriate place for the encryption. In various embodiments, asubscriber identification and/or an authentication key is decrypted in awireless terminal, in a SIM card, or in a combination of the SIM cardand the wireless terminal, or in any other appropriate place for thedecryption. In some embodiments, authentication information isreceived—for example, a random number that has been encrypted using anauthentication key, a subscriber identification that has been encryptedusing an authentication key, or other information that has beenencrypted using an authentication key or other appropriate key. In 608,wireless service is acquired from the wireless network using the secondsubscriber identification.

Wireless Communication Provisioning Using State Transition Rules

Wireless communication provisioning using state transition rulesassociated with an identifier is disclosed. A first state associatedwith one or more identifiers is defined. A second state associated withone or more identifiers is defined. A state transition rule is definedbetween the first and second states. In some embodiments, the one ormore identifiers are stored in a subscriber identity module (SIM). Insome embodiments, a plurality of states are defined, a plurality ofstate transition rules are defined, and a group of states and transitionrules are selected and associated with one or more identifiers. In someembodiments, wireless communications comprise mobile data, mobilecellular communications, or any other appropriate wirelesscommunications.

In some embodiments, a customer organization defines a sequence ofstates for devices that communicate data with a global platformprovider's application server via one or more wireless carrier networks.The provider (e.g., the global platform provider) enables thecommunication via the wireless carrier networks. The plurality of statesenables the activity of provisioning of a customer device or providerdevice used in the data communication with appropriate billing, access,and/or authorization for each activity especially with regard totesting, activation, deactivation, etc.

FIG. 7 illustrates a block diagram of an embodiment of a system formobile data communication provisioning. In the example shown, device 700comprises a mobile device that communicates data. Device 700 includes amobile data service (MDS) 702—for example, general packet radioservice—and an identifier (ID) 704—for example, a subscriber identifier(such as IMSI). Data can be transmitted and received by device 700 usingMDS 702. Device 700 is identified using ID 704 and associated with auser or customer. Transmissions and receptions of data communicate withcarrier network 712, which is associated with MDS 702. In variousembodiments, the carrier network associated with MDS 702 comprises amobile carrier network, a cell phone network, a messaging network,wireless communication network, or any other appropriate network forcommunicating data to a mobile device.

Carrier network 712 includes carrier switching network 710 (e.g.,SGSN—serving General Packet Radio Services (GPRS) support node—used inGlobal System for Mobile Communications (GSM) networks), carrier datatraffic handler 708 (e.g., GRX—a GPRS roaming exchange and/orSS7—signaling system 7 system), and a plurality of carriertowers—represented in FIG. 7 by tower 706. Communications of datatraffic to and from device 700 are received by carrier network 712 by acarrier tower, which communicates the data traffic with carrier datatraffic handler 708. Carrier data traffic handler 708 communicates datatraffic with carrier switching network 710. Carrier switching network710 can communicate with network 714, and Authentication Center/HomeLocation Register (HLR) 728 and Authentication, Authorization, andAccounting (AAA) Server (e.g., a Radius server) 730 of provider system724. In one embodiment, provider system 724 is operated by a globalplatform provider as a control center.

Network 714 enables communication with customer system 716, whichincludes customer application server 718 and customer administrator 720.In some embodiments, network 714 comprises the internet, a local areanetwork, a wide area network, a wired network, a wireless network, orany other appropriate network or networks for communicating withcustomer system 716. Customer application server 718 receives data fromand transmits data to device 700 regarding the customer's services orproducts. In various embodiments, the customer's services includestransaction related services, monitoring services, and/or locationtracking services. In some embodiments, a state transition rule definingtransition from one provisioning state to another provisioning stateassociated with device 700 is implemented on customer application server718. In some embodiments, a state transition rule defining transitionfrom one provisioning state to another provisioning state associatedwith device 700 is not known to device 700.

Provider system 724 includes HLR 728, AAA server 730, application server726, database (DB) 732, administrator 734. In an embodiment where theprovider system 724 is the control center of a global platform provider,application server 726 can perform the function of a provisioningserver, such as provisioning server 110 of FIG. 1, in addition to otherfunctions. Provider system 724 enables customer services by enablingdata communication services via the carrier network with device 700. HLR728 enables communication with the provider system by indicating ifdevice 700 is allowed to have data communication through carrier network712 with customer system 716. AAA server 730 enables specificpermissions that are available regarding data communications betweendevice 700 and customer system 716 via carrier network 712. Applicationserver 726 enables provisioning and billing for the provider.Provisioning comprises enabling devices such as device 700 to havemobile data communication services using a mobile carrier network. DB732 includes information related to provisioning and billing for theprovider. Administrator 734 administrates provider system. Customersystem administrator 720 communicates with provider application server726 to administrate customer system usage, billing, provisioning fordata communication service of carrier network 712 enable by provider724. In some embodiments, functionality of HLR 728 and AAA server 730are performed by the same server, are partitioned between two serversbut not exactly as described herein, or any other server configurationto achieve the same functionality.

FIG. 8 is a flow diagram illustrating an embodiment of a process formobile data communication provisioning. In some embodiments, the processof FIG. 8 helps provision device 700 of FIG. 7 such that mobile dataand/or wireless communications is available via carrier network 712 tocustomer system 716. In the example shown, in 800 states associated withone or more identifiers are defined. States that are associated with oneor more identifiers can include test ready, inventory, activation ready,activated, deactivated, retired, return merchandise authorization (RMA),suspend, fraud review, purged, and/or any other appropriate states. Invarious embodiments, the identifier can be an International Circuit CardIdentifier (ICCID), an international mobile subscriber identifier(IMSI), a customer identifier, a user identifier, or a deviceidentifier. In various embodiments, the one or more identifierscomprises an identifier associated with a user, a customer, a company,an organization, etc. or a group of identifiers associated with a user,a customer, a company, an organization, etc.

In some embodiments, one or more states are based on the lifecycle ofthe service of a wireless communication device.

A test ready state can be used to allow a manufacturer to test a SIM, ora device with a SIM, and its network communication infrastructure beforedelivering the SIM, or device with a SIM, to an end user, a retaillocation, or a distributor. A test ready state can be a default statefor a SIM that allows authentication and authorization with a globalplatform provider's HLR and AAA server, but does not have any billingassociated with it. A SIM in a test ready state is able to conditionallytransact data, voice, and/or Short Message Service (SMS)communications—for example, some limits may be placed on thecommunications while in this state such as: communication may occur upto a maximum data transmitted/received amount or up to a maximum numberof days since the initial data communication. A test ready state mayhave no prerequisite state, have no limitation to a next state (e.g.,all states allowed as next state), have no exclusivity rule, be arequired state, and be allowed to have automatic and/or manualtransitions.

An inventory state can be used to allow a SIM to be placed in a deviceand associated with an identifier of the device (e.g., a terminalidentifier or a point of sale terminal identifier). An inventory statecannot coexist with an activation ready state. An inventory state cannotconnect with the network and requires a manual change in order to changestate. An inventory state may have a test ready state as a prerequisite,have no limitation to a next state (e.g., all states allowed as nextstate), have an exclusivity rule in that it cannot coexist with anactivation ready state, not is a required state, and be allowed only tohave manual transitions.

An activation ready state can be used to allow a SIM to be ready to beactivated. An activation ready state will authenticate and authorizewith the HLR and AAA server of the provider system, but no billing willoccur. After the first data communication (e.g., first packet dataprotocol (PDP) context communication), the SIM state will automaticallychange to an activated state. An activation ready state may have a testready state or inventory state as a prerequisite, have no limitation toa next state (e.g., all states allowed as next state), have anexclusivity rule in that it cannot coexist with an inventory state, notbe a required state, and be allowed to have an automatic transition toan activated state or a manual transition to other states.

An activated state can be used to allow a SIM, or a device with a SIM,to be used by a user. In an activated state the SIM will authenticateand authorize on the HLR and AAA server of the provider system. Billingcommences immediately on changing to this state. The provider system maycheck to make sure that the proper information is contained on theprovider system's HLR and AAA server databases as well as the billingdatabases. In some cases, the checks will include checking theidentifiers stored in the SIM (e.g., international mobile subscriberidentifier (IMSI), customer identifier, device identifier, etc.). Anactivated state may have a test ready state, inventory, or activationready state as a prerequisite, have possible next states of deactivated,purged, or retired, have no exclusivity rule, not be a required state,and be only allowed to have a manual transition to a next state.

A deactivated state can be used to allow a SIM, or a device with a SIM,to be deactivated by the user. In a deactivated state the SIM will notbe allowed to authenticate and will not be billed. The AAA server of theprovider system and the gateway GPRS support node (GGSN) of carriernetworks will be sent a notification (e.g., a packet) informing themthat the SIM has been deactivated. An deactivated state may have anactivated state as a prerequisite, have possible next states ofactivated, purged, or retired, have no exclusivity rule, not be arequired state, and be only allowed to have a manual transition to anext state.

A retired state can be used to allow a SIM, or a device with a SIM, tobe retired by the provider or the user. In a retired state the SIM willnot be allowed to authenticate and billing ends. A retired state mayhave any state as a prerequisite except purged, have any possible nextstates (i.e., all states possible), have no exclusivity rule, not be arequired state, and be only allowed to have a manual transition to anext state.

A purged state can be used to allow a SIM, or a device with a SIM, to bepurged by the provider. In a purged state the SIM will not be allowed toauthenticate and the subscriber identification is removed from thesystem (e.g., IMSI permanently removed from the HLR of the providersystem). A purged state may have any state as a prerequisite, have nopossible next states, have no exclusivity rule, not be a required state,and be not allowed to have any transitions to a next state.

In some embodiments, a state is defined by a customer. In someembodiments, the state is defined using an Internet-based service.

In some embodiments, a state definition does not support communicationsessions and a transition to that state will terminate existing opencommunication sessions.

In some embodiments, a first wireless communication provisioning stateallows a communication device to pass traffic without incurring anybilling charges, and an associated state transition rule allows anautomated transition to a second provisioning state where the secondprovisioning state incurs billing charges. In some embodiments, a firstwireless communication provisioning state allows a communication deviceto pass traffic without incurring any billing charges, and an associatedstate transition rule allows an automated transition to the secondprovisioning state, where the second provisioning state does not allowthe communication device to pass traffic.

In 802, state transition rule(s) between two states is/are defined. Atransition from one state to another may occur automatically on apredetermined condition or manually. If the transition is based on acondition is met (e.g., upon first data communication—packet dataprotocol context established), the state will automatically change fromone to another (e.g., activation ready state to activated state). Invarious embodiments, the transition condition is based on one or more ofthe following: a predetermined amount of elapsed time since a priorstate transition, an amount of service usage above a predeterminedamount of service usage, one or more service signalings, or any otherappropriate condition. In various embodiments, the condition is based onan exclusivity rule, a state rule, a communication data transfer, or anyother appropriate condition. A manual change from one state to anotherrequires an intervention directly from the provider system—for example,an action through a manager portal, by uploading a file to the SIM ordevice with the SIM, or an application programming interface (API) call.

In various embodiments, a state transition rule can be defined for anindividual device or a group of devices, or different rules can bedefined for different individual devices or different groups of devices,or any other appropriate combination as appropriate for meeting theneeds of a supplier of devices.

In some embodiments, a group of states are defined and a group oftransition rules are defined, and then a selection of states andtransition rules are associated with one or more identifiers.

In some embodiments, a customer selects a state transition rule. In someembodiments, a customer defines a state transition rule. In variousembodiments, the state transition rule is selected and/or defined usingan Internet-based service, using a local program interface, or any otherappropriate manner of selecting and defining a state transition rule.

In some embodiments, a state transition rule when activated terminatesexisting communication sessions.

FIG. 9 is a block diagram illustrating an embodiment of a statedefinition. In some embodiments, a state is associated with anidentifier—for example, a SIM, a device identifier (e.g., aninternational mobile equipment identifier), a vendor identifier, or anyother appropriate identifier. In the example shown, a state definitionincludes state name, state description, required state flag,prerequisite state, allowed next state(s), exclusivity rule, andtransition mode(s) available that describe conditions allowingtransitions between states. For example, a test ready state has: a) astate name of test ready; b) a state description of SIM is able totested in its operation with the network by a manufacturer in a limitedmanner without being billed; c) a required state flag indicating thatthe test ready state is required; d) there is no prerequisite state forthe test ready state; e) allowed next states from test ready areinventory, activation ready, activated, retired, or purged; f) there isno exclusivity rule for the test ready state; and g) the transitionmodes available are automatic to either an inventory state or anactivation ready state based on an exclusivity rule or manual change.

FIG. 10 illustrates an embodiment of a state transition rule definition.In various embodiments, a state transition rule definition is associatedwith a state associated with an identifier or an identifier. In theexample shown, a state transition rule definition includes currentstate, transition condition, state transitioned to, and transitiondescription. For example, a SIM can be manually changed from aninventory state to an activation ready state when the device that theSIM is in is deployed by selling the unit to a retail customer, byhaving a service provider place the unit in the field, or by any otherappropriate manner. For another example, a SIM can be automaticallychanged from an activation ready state to an active state when a PDPcontext is established and data is communicated to and from the SIM, ordevice with the SIM in it.

FIG. 11 is a flow diagram illustrating an embodiment of states of achannel sale model for provisioning and the transitions between thestates. In some embodiments, the starting default state of a SIM is thetest ready state. In the example shown, in test ready state 1100 adevice is ready for testing. The SIM is shipped in the test ready stateto an original equipment manufacturer (OEM)—for example, a customerwanting to use the connectivity services provided by the provider whichenables a user's device to have data communication to the customer viaone or more carrier networks. In test ready state 1100, the SIM isallowed to provision and establish a PDP session (e.g., it can connectto GGSN of a carrier network, connect to internet, and connect to thecustomer's application server). When the SIM is in the test ready state,no billing to the OEM occurs. This connectivity is allowed for until thetransition 1101. Transition 1101 from the test ready state is either amanually triggered transition or an automatically triggered based on acondition where the condition is the when the SIM has reached: 1) amaximum number of PDP sessions has occurred—for example, 10; 2) amaximum amount of data has been transmitted/received to and from theSIM/device via the carrier network—for example, 100 Kbytes; or 3) amaximum amount of time has elapsed since the first PDP context in thistest ready state—for example, 90 days. When the transition is triggered,then the SIM switches to inventory state 1102.

In inventory state 1102, a device is waiting to be transferred to auser. In this state, no connectivity is enabled, and no billing occurs.The state is maintained until transition 1103. Transition 1103 occurswhen the OEM or the customer or its channel service providers manuallytriggers a state change. When the state change is triggered, the SIM ischanged to activated state 1104. In activated state 1104, a device isbeing used by user. In activated state 1104, the SIM is able toestablish a PDP session and connect and transfer data to a customerapplication server via a carrier network. The user is billed for theservice provided by the provider. Billing information is provided to thecustomer by gathering the relevant data from the network carriers andthe provider's data bases. The SIM remains in the active state untiltriggered to transition. Transition 1105 may be triggered manually orautomatically. In various embodiments, transition 1105 is triggeredautomatically by a maximum number of connections allowed, a maximumamount of data transferred, a maximum amount of time since the start ofPDP sessions, or any other appropriate automatic trigger condition. Insome embodiments, the user or the customer can also manually triggertransition 1105 to a deactivated state 1106.

In deactivated state 1106, a device is finished being used as requestedby an end user or by a customer system request by being in a deactivatedstate. In deactivated state 1106, the SIM is not able to connect andestablish a PDP session. While in deactivated state 1106, there is nobilling for connectivity. Transition 1107 can be triggered automatically(e.g., after a period of time) or manually (e.g., by the customer). Whentransition 1107 is triggered, the SIM changes state to purged state1108. In purged state 1108, the SIM and the device the SIM is in, isremoved from the system. In purged state 1108, the SIM is not able toconnect and establish a PDP session. There is no billing associated withthe trigger or the state. Accounting for the customer may remove theitem from inventory or asset lists. Purged state 1108 automaticallyremoves the IMSI and International Circuit Card Identifier (ICCID) fromthe HLR of the provider system.

FIG. 12 is a flow diagram illustrating an embodiment of states of aretail sale model for provisioning and the transitions between thestates. The states and transitions in FIG. 12 are similar to the statesand transitions in FIG. 11 except for the activation ready state. Insome embodiments, the starting default state of a SIM is the test readystate. In the example shown, in test ready state 1200 a device is readyfor testing. The SIM is shipped in the test ready state to an originalequipment manufacturer (OEM)—for example, a customer wanting to use theconnectivity services provided by the provider which enables a user'sdevice to have data communication to the customer via one or morecarrier networks. In test ready state 1200, the SIM is allowed toprovision and establish a PDP session (e.g., it can connect to GGSN of acarrier network, connect to internet, and connect to the customer'sapplication server). When the SIM is in the test ready state, no billingto the OEM occurs. This connectivity is allowed for until the transition1201. Transition 1201 from the test ready state is either a manuallytriggered transition or an automatically triggered based on a conditionwhere the condition is the when the SIM has reached: 1) a maximum numberof PDP sessions has occurred—for example, 5; 2) a maximum amount of datahas been transmitted/received to and from the SIM/device via the carriernetwork—for example, 1 Mbytes; or 3) a maximum amount of time haselapsed since the first PDP context in this test ready state—forexample, 1 year. When the transition is triggered, then the SIM switchesto activation ready state 1202.

In activation ready state 1202, a device is waiting to be transferred toa user. In various embodiments, the activation ready state is set aftertesting by the OEM when the device is being shipped from the OEM toretail locations, distribution partners, directly to end users, or whenthe SIM, or device with the SIM, is about to be in the end users handsbut is not ready to have billing/service fully implemented. In thisstate, SIM connectivity is enabled, and a PDP session can beestablished. Upon the first PDP session occurring transition 1203 istriggered. When the state change is triggered, the SIM is changed toactivated state 1204. In activated state 1204, a device is being used byuser. In activated state 1204, the SIM is able to establish a PDPsession and connect and transfer data to a customer application servervia a carrier network. The user is billed for the service provided bythe provider. Billing information is provided to the customer bygathering the relevant data from the network carriers and the provider'sdata bases. The SIM remains in the active state until triggered totransition. Transition 1205 may be triggered manually or automatically.In various embodiments, transition 1205 is triggered automatically by amaximum number of connections allowed, a maximum amount of datatransferred, a maximum amount of time since the start of PDP sessions,or any other appropriate automatic trigger condition. In someembodiments, the user or the customer can also manually triggertransition 1205 to a deactivated state 1206.

In deactivated state 1206, a device is finished being used as requestedby an end user or by a customer system request by being in a deactivatedstate. In deactivated state 1206, the SIM is not able to connect andestablish a PDP session. While in deactivated state 1206, there is nobilling for connectivity. Transition 1207 can be triggered automatically(e.g., after a period of time) or manually (e.g., by the customer). Whentransition 1207 is triggered, the SIM changes state to purged state1208. In purged state 1208, the SIM and the device the SIM is in, isremoved from the system. In purged state 1208, the SIM is not able toconnect and establish a PDP session. There is no billing associated withthe trigger or the state. Accounting for the customer may remove theitem from inventory or asset lists. Purged state 1208 automaticallyremoves the IMSI and International Circuit Card Identifier (ICCID) fromthe HLR of the global platform provider system.

FIG. 13 is a flow diagram illustrating an embodiment of a process forprovisioning wireless communication. In the example shown, in 1300definitions for states associated with an identifier are received. Insome embodiments, state definitions and/or selections are received usingan internet-based application. In various embodiments, state definitionsare the same or different for different identifiers. In variousembodiments, a state for provisioning (e.g., a device) allows billing,allows communication sessions, allows activation, does not allowbilling, does not allow communication sessions, does not allowactivation, or any other appropriate action associated with a state. In1302, definition(s) for state transition rule(s) between two statesis/are received. In some embodiments, state transition rule definitionsand/or selections are received using an internet-based application. Invarious embodiments, the transitions are automatic or manual and aretriggered with a transition condition. In various embodiments, theautomatic and/or manual transition conditions include an elapsed timefrom a prior state, prior transition, or prior specific/anycommunication, an absolute time, an absolute date, after a predeterminedamount of traffic, before a predetermined level of traffic is reached,after communication with a specific location, number, device, servicecenter, after sending a service indication, a system message, afterreceipt of a service message, condition, communication from a specificlocation, device, server, service center, or any other appropriatetransition condition. In 1304, it is determined if a transitioncondition associated with a transition rule for current state is met. Inthe event that an appropriate transition condition has not been met,control stays with 1304. In the event that an appropriate transitioncondition is met, then in 1306 allow transition between the two statesas appropriate for the transition rule. In some embodiment, theimplementation of provisioning states, state transition ruleenforcement, and evaluation of transition conditions takes place on aserver that communicates with a wireless network and wireless device. Inone embodiment, the server is located in, or otherwise operated by, aglobal platform provider's control center.

Although the foregoing embodiments have been described in some detailfor purposes of clarity of understanding, the invention is not limitedto the details provided. There are many alternative ways of implementingthe invention. The disclosed embodiments are illustrative and notrestrictive.

What is claimed is:
 1. A server system for wireless communicationprovisioning of a wireless communication device operating in a carriernetwork including at least one carrier tower comprising: a processor;and a memory coupled with the processor, wherein the memory isconfigured to provide the processor with instructions which whenexecuted cause the processor to: detect that a transition condition hasoccurred in a lifecycle of the wireless communication device, whereinthe transition condition indicates that an authorized user of thewireless communication device has changed or a usage condition of theauthorized user has expired; determine a current provisioning stateassociated with the one or more identifiers; determine a nextprovisioning state associated with the one or more identifiers;determine a state transition rule associated with the one or moreidentifiers wherein the state transition rule defines a transitionbetween the current provisioning state and the next provisioning state;determine a provisioning instruction according to an occurrence of thetransition condition and an application of the state transition rule;and transmit the provisioning instruction to at least one of anAuthentication Center (AuC), a Home Location Register (HLR), a GatewayGPRS Support Node (GGSN), a Billing system, or an AuthenticationAuthorization Accounting (AAA) system according to the state transitionrule.
 2. A system as in claim 1, wherein the current provisioning statecomprises a non-billable state and the next provisioning state comprisesa billable state.
 3. A system as in claim 1, wherein the currentprovisioning state comprises a billable state and the next provisioningstate comprises a non-billable state.
 4. A system as in claim 1, whereinthe current provisioning state comprises one or more of the following: astate name, a state description, a required state flag, a prerequisitestate, an allowed next state, an exclusivity rule, or a transition mode.5. A system as in claim 1, wherein the current provisioning state allowsat least one of the following: an authentication for communication, anauthorization for communication, an automatic transition to the nextprovisioning state, an activated state or no billing for communication.6. A system as in claim 1, wherein an identifier of the one or moreidentifiers comprises at least one of the following: a SIM, a ICCID, oran IMSI.
 7. A system as in claim 1, wherein the state transition rulecomprises indicating an automated state transition based on thetransition condition.
 8. A system as in claim 1, wherein the transitioncondition is based on one or more of the following: a predeterminedamount of elapsed time since a prior state transition, an amount ofservice usage above a predetermined amount of service usage, a locationupdate, an application programming interface (API) call, and a networkregistration.
 9. A system as in claim 1, wherein the state transitionrule is defined for a wireless communication device.
 10. A system as inclaim 1, wherein the state transition rule is defined for a firstwireless communication device that is different from the statetransition rule for a second wireless communication device.
 11. A systemas in claim 1, wherein the state transition rule is defined for a groupof wireless communication device.
 12. A system as in claim 1, wherein acustomer selects the state transition rule.
 13. A system as in claim 1,wherein a customer defines the state transition rule.
 14. A system as inclaim 1, wherein a customer defines the current provisioning state. 15.A system as in claim 1, wherein a customer defines the next provisioningstate.
 16. A system as in claim 1, wherein the current provisioningstate does not include support for a communication session.
 17. A systemas in claim 16, wherein upon entering the current provisioning state,terminating an existing communication session.
 18. A system as in claim1, wherein the transition rule when activated terminates existingcommunication sessions.
 19. A system as in claim 1, wherein the currentprovisioning state allows a communication device to pass traffic withoutincurring any billing charges, and wherein the state transition ruleallows an automated transition to the next provisioning state, andwherein the next provisioning state incurs billing charges.
 20. A systemas in claim 1, wherein the current provisioning state allows acommunication device to pass traffic without incurring any billingcharges, and wherein the state transition rule allows an automatedtransition to the next provisioning state, and wherein the nextprovisioning state does not allow the communication device to passtraffic.
 21. A system as in claim 1, wherein the state transition rulecomprises indicating a manual state transition based on one or more ofthe following transition conditions: an action through a manager portal,by uploading a file to the SIM or device with the SIM, or an applicationprogramming interface (API) call.
 22. A system as in claim 1, wherein anidentifier of the one or more identifiers comprises at least one of thefollowing: a customer identifier, a user identifier, or a deviceidentifier.
 23. A method for wireless communication provisioning of awireless communication device operating in a carrier network includingat least one carrier tower comprising: detect that a transitioncondition has occurred in a lifecycle of the wireless communicationdevice, wherein the transition condition indicates that an authorizeduser of the wireless communication device has changed or a usagecondition of the authorized user has expired; determining a currentprovisioning state associated with the one or more identifiers;determining a next provisioning state associated with the one or moreidentifiers; determining a state transition rule associated with the oneor more identifiers wherein the state transition rule defines atransition between the current provisioning state and the nextprovisioning state; determining a provisioning instruction according toan occurrence of a transition condition and an application of the statetransition rule; and transmitting the provisioning instruction to atleast one of an Authentication Center (AuC), a Home Location Register(HLR), a Gateway GPRS Support Node (GGSN), a Billing system, or anAuthentication Authorization Accounting (AAA) system according to thestate transition rule.
 24. A computer program product for wirelesscommunication provisioning of a wireless communication device operatingin a carrier network including at least one carrier tower, the computerprogram product being embodied in a non-transitory computer readablemedium and comprising computer instructions to: detect that a transitioncondition has occurred in a lifecycle of the wireless communicationdevice, wherein the transition condition indicates that an authorizeduser of the wireless communication device has changed or a usagecondition of the authorized user has expired; determine a currentprovisioning state associated with the one or more identifiers;determine a next provisioning state associated with the one or moreidentifiers; determine a state transition rule associated with the oneor more identifiers wherein the state transition rule defines atransition between the current provisioning state and the nextprovisioning state; determine a provisioning instruction according to anoccurrence of a transition condition and an application of the statetransition rule; and transmit the provisioning instruction to at leastone of an Authentication Center (AuC), a Home Location Register (HLR), aGateway GPRS Support Node (GGSN), a Billing system, or an AuthenticationAuthorization Accounting (AAA) system according to the state transitionrule.